Method and apparatus for handling beam failure recovery regarding cell deactivation in a wireless communication system

ABSTRACT

A method and apparatus are disclosed. In an example from the perspective of a User Equipment (UE), the UE triggers a first beam failure recovery (BFR) associated with a first cell. In response to the first triggered BFR, the UE triggers a Scheduling Request (SR) for Secondary Cell (SCell) beam failure recovery. In response to deactivation of the first cell, the UE cancels the first triggered BFR and the triggered SR for SCell beam failure recovery associated with the first cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to and is a continuation of U.S.application Ser. No. 17/111,797, filed on Dec. 4, 2020, entitled “METHODAND APPARATUS FOR HANDLING BEAM FAILURE RECOVERY REGARDING CELLDEACTIVATION IN A WIRELESS COMMUNICATION SYSTEM”, the entire disclosureof which is incorporated herein in its entirety by reference. U.S.application Ser. No. 17/111,797 claims the benefit of U.S. ProvisionalPatent Application Ser. No. 62/944,572 filed on Dec. 6, 2019, the entiredisclosure of which is incorporated herein in its entirety by reference.

FIELD

This disclosure generally relates to wireless communication networks,and more particularly, to a method and apparatus for handling beamfailure recovery regarding cell deactivation in a wireless communicationsystem.

BACKGROUND

With the rapid rise in demand for communication of large amounts of datato and from mobile communication devices, traditional mobile voicecommunication networks are evolving into networks that communicate withInternet Protocol (IP) data packets. Such IP data packet communicationcan provide users of mobile communication devices with voice over IP,multimedia, multicast and on-demand communication services.

An exemplary network structure is an Evolved Universal Terrestrial RadioAccess Network (E-UTRAN). The E-UTRAN system can provide high datathroughput in order to realize the above-noted voice over IP andmultimedia services. A new radio technology for the next generation(e.g., 5G) is currently being discussed by the 3GPP standardsorganization. Accordingly, changes to the current body of 3GPP standardare currently being submitted and considered to evolve and finalize the3GPP standard.

SUMMARY

In accordance with the present disclosure, one or more devices and/ormethods are provided. In an example from the perspective of a UserEquipment (UE), the UE triggers a first beam failure recovery (BFR)associated with a first cell. In response to the first triggered BFR,the UE triggers a Scheduling Request (SR) for Secondary Cell (SCell)beam failure recovery. In response to deactivation of the first cell,the UE cancels the first triggered BFR and the triggered SR for SCellbeam failure recovery associated with the first cell.

In an example from the perspective of a UE, the UE triggers a first BFRassociated with a first cell. In response to the first triggered BFR,the UE triggers a SR for SCell beam failure recovery. In response todeactivation of the first cell, the UE cancels the first triggered BFRand one of stops SR transmission for SCell beam failure recovery if theUE does not have an activated cell associated with a second triggeredBFR, or does not stop the SR transmission for SCell beam failurerecovery if the UE has an activated cell associated with the secondtriggered BFR.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a wireless communication system according toone exemplary embodiment.

FIG. 2 is a block diagram of a transmitter system (also known as accessnetwork) and a receiver system (also known as user equipment or UE)according to one exemplary embodiment.

FIG. 3 is a functional block diagram of a communication system accordingto one exemplary embodiment.

FIG. 4 is a functional block diagram of the program code of FIG. 3according to one exemplary embodiment.

FIG. 5 is a diagram illustrating an exemplary scenario associated with atriggered beam failure recovery (BFR) according to one exemplaryembodiment.

FIG. 6 is a diagram illustrating an exemplary scenario associated with atriggered BFR according to one exemplary embodiment.

FIG. 7 is a diagram illustrating an exemplary scenario associated with atriggered BFR according to one exemplary embodiment.

FIG. 8 is a diagram illustrating an exemplary scenario associated with atriggered BFR according to one exemplary embodiment.

FIG. 9 is a flow chart according to one exemplary embodiment.

FIG. 10 is a flow chart according to one exemplary embodiment.

FIG. 11 is a flow chart according to one exemplary embodiment.

FIG. 12 is a flow chart according to one exemplary embodiment.

FIG. 13 is a flow chart according to one exemplary embodiment.

DETAILED DESCRIPTION

The exemplary wireless communication systems and devices described belowemploy a wireless communication system, supporting a broadcast service.Wireless communication systems are widely deployed to provide varioustypes of communication such as voice, data, and so on. These systems maybe based on code division multiple access (CDMA), time division multipleaccess (TDMA), orthogonal frequency division multiple access (OFDMA),3^(rd) Generation Partnership Project (3GPP) LTE (Long Term Evolution)wireless access, 3GPP LTE-A or LTE-Advanced (Long Term EvolutionAdvanced), 3GPP2 UMB (Ultra Mobile Broadband), WiMax, 3GPP NR (NewRadio) wireless access for 5G, or some other modulation techniques.

In particular, the exemplary wireless communication systems devicesdescribed below may be designed to support one or more standards such asthe standard offered by a consortium named “3rd Generation PartnershipProject” referred to herein as 3GPP, including: 3GPP TS 38.321, V15.7.0,Medium Access Control (MAC) protocol specification; R2-1915254, MACRunning CR for NR eMIMO, Samsung; R1-1909833, Reply LS on MAC CE designfor SCell BFR, Apple; 3GPP RAN2 #108 meeting report; 3GPP RAN2 #107bismeeting report. The standards and documents listed above are herebyexpressly incorporated by reference in their entirety.

FIG. 1 presents a multiple access wireless communication system inaccordance with one or more embodiments of the disclosure. An accessnetwork 100 (AN) includes multiple antenna groups, one including 104 and106, another including 108 and 110, and an additional including 112 and114. In FIG. 1, only two antennas are shown for each antenna group,however, more or fewer antennas may be utilized for each antenna group.Access terminal 116 (AT) is in communication with antennas 112 and 114,where antennas 112 and 114 transmit information to access terminal 116over forward link 120 and receive information from access terminal 116over reverse link 118. AT 122 is in communication with antennas 106 and108, where antennas 106 and 108 transmit information to AT 122 overforward link 126 and receive information from AT 122 over reverse link124. In a frequency-division duplexing (FDD) system, communication links118, 120, 124 and 126 may use different frequencies for communication.For example, forward link 120 may use a different frequency than thatused by reverse link 118.

Each group of antennas and/or the area in which they are designed tocommunicate is often referred to as a sector of the access network. Inthe embodiment, antenna groups each may be designed to communicate toaccess terminals in a sector of the areas covered by access network 100.

In communication over forward links 120 and 126, the transmittingantennas of access network 100 may utilize beamforming in order toimprove the signal-to-noise ratio of forward links for the differentaccess terminals 116 and 122. Also, an access network using beamformingto transmit to access terminals scattered randomly through its coveragemay normally cause less interference to access terminals in neighboringcells than an access network transmitting through a single antenna toits access terminals.

An access network (AN) may be a fixed station or base station used forcommunicating with the terminals and may also be referred to as anaccess point, a Node B, a base station, an enhanced base station, aneNodeB (eNB), a Next Generation NodeB (gNB), or some other terminology.An access terminal (AT) may also be called user equipment (UE), awireless communication device, terminal, access terminal or some otherterminology.

FIG. 2 presents an embodiment of a transmitter system 210 (also known asthe access network) and a receiver system 250 (also known as accessterminal (AT) or user equipment (UE)) in a multiple-input andmultiple-output (MIMO) system 200. At the transmitter system 210,traffic data for a number of data streams may be provided from a datasource 212 to a transmit (TX) data processor 214.

In one embodiment, each data stream is transmitted over a respectivetransmit antenna. TX data processor 214 formats, codes, and interleavesthe traffic data for each data stream based on a particular codingscheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot datausing orthogonal frequency-division multiplexing (OFDM) techniques. Thepilot data may typically be a known data pattern that is processed in aknown manner and may be used at the receiver system to estimate thechannel response. The multiplexed pilot and coded data for each datastream may then be modulated (i.e., symbol mapped) based on a particularmodulation scheme (e.g., binary phase shift keying (BPSK), quadraturephase shift keying (QPSK), M-ary phase shift keying (M-PSK), or M-aryquadrature amplitude modulation (M-QAM)) selected for that data streamto provide modulation symbols. The data rate, coding, and/or modulationfor each data stream may be determined by instructions performed byprocessor 230.

The modulation symbols for data streams are then provided to a TX MIMOprocessor 220, which may further process the modulation symbols (e.g.,for OFDM). TX MIMO processor 220 then provides N_(T) modulation symbolstreams to N_(T) transmitters (TMTR) 222 a through 222 t. In certainembodiments, TX MIMO processor 220 may apply beamforming weights to thesymbols of the data streams and to the antenna from which the symbol isbeing transmitted.

Each transmitter 222 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and/or upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. N_(T)modulated signals from transmitters 222 a through 222 t may then betransmitted from N_(T) antennas 224 a through 224 t, respectively.

At receiver system 250, the transmitted modulated signals are receivedby N_(R) antennas 252 a through 252 r and the received signal from eachantenna 252 may be provided to a respective receiver (RCVR) 254 athrough 254 r. Each receiver 254 may condition (e.g., filters,amplifies, and downconverts) a respective received signal, digitize theconditioned signal to provide samples, and/or further process thesamples to provide a corresponding “received” symbol stream.

An RX data processor 260 then receives and/or processes the N_(R)received symbol streams from N_(R) receivers 254 based on a particularreceiver processing technique to provide N_(T) “detected” symbolstreams. The RX data processor 260 may then demodulate, deinterleave,and/or decode each detected symbol stream to recover the traffic datafor the data stream. The processing by RX data processor 260 may becomplementary to that performed by TX MIMO processor 220 and TX dataprocessor 214 at transmitter system 210.

A processor 270 may periodically determine which pre-coding matrix touse (discussed below). Processor 270 formulates a reverse link messagecomprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message may then be processed by a TX data processor 238,which may also receive traffic data for a number of data streams from adata source 236, modulated by a modulator 280, conditioned bytransmitters 254 a through 254 r, and/or transmitted back to transmittersystem 210.

At transmitter system 210, the modulated signals from receiver system250 are received by antennas 224, conditioned by receivers 222,demodulated by a demodulator 240, and processed by a RX data processor242 to extract the reserve link message transmitted by the receiversystem 250. Processor 230 may then determine which pre-coding matrix touse for determining the beamforming weights and may then process theextracted message.

FIG. 3 presents an alternative simplified functional block diagram of acommunication device according to one embodiment of the disclosedsubject matter. As shown in FIG. 3, the communication device 300 in awireless communication system can be utilized for realizing the UEs (orATs) 116 and 122 in FIG. 1 or the base station (or AN) 100 in FIG. 1,and the wireless communications system may be the LTE system or the NRsystem. The communication device 300 may include an input device 302, anoutput device 304, a control circuit 306, a central processing unit(CPU) 308, a memory 310, a program code 312, and a transceiver 314. Thecontrol circuit 306 executes the program code 312 in the memory 310through the CPU 308, thereby controlling an operation of thecommunications device 300. The communications device 300 can receivesignals input by a user through the input device 302, such as a keyboardor keypad, and can output images and sounds through the output device304, such as a monitor or speakers. The transceiver 314 is used toreceive and transmit wireless signals, delivering received signals tothe control circuit 306, and outputting signals generated by the controlcircuit 306 wirelessly. The communication device 300 in a wirelesscommunication system can also be utilized for realizing the AN 100 inFIG. 1.

FIG. 4 is a simplified block diagram of the program code 312 shown inFIG. 3 in accordance with one embodiment of the disclosed subjectmatter. In this embodiment, the program code 312 includes an applicationlayer 400, a Layer 3 portion 402, and a Layer 2 portion 404, and iscoupled to a Layer 1 portion 406. The Layer 3 portion 402 may performradio resource control. The Layer 2 portion 404 may perform linkcontrol. The Layer 1 portion 406 may perform and/or implement physicalconnections.

Uplink (UL) data transfer is introduced in 3GPP TS 38.321, V15.7.0:

5.4 UL-SCH Data Transfer 5.4.1 UL Grant Reception

Uplink grant is either received dynamically on the PDCCH, in a RandomAccess Response, or configured semi-persistently by RRC. The MAC entityshall have an uplink grant to transmit on the UL-SCH. To perform therequested transmissions, the MAC layer receives HARQ information fromlower layers.If the MAC entity has a C-RNTI, a Temporary C-RNTI, or CS-RNTI, the MACentity shall for each PDCCH occasion and for each Serving Cell belongingto a TAG that has a running timeAlignmentTimer and for each grantreceived for this PDCCH occasion:

-   -   1> if an uplink grant for this Serving Cell has been received on        the PDCCH for the MAC entity's C-RNTI or Temporary C-RNTI; or    -   1> if an uplink grant has been received in a Random Access        Response:        -   2> if the uplink grant is for MAC entity's C-RNTI and if the            previous uplink grant delivered to the HARQ entity for the            same HARQ process was either an uplink grant received for            the MAC entity's CS-RNTI or a configured uplink grant:            -   3> consider the NDI to have been toggled for the                corresponding HARQ process regardless of the value of                the NDI.        -   2> if the uplink grant is for MAC entity's C-RNTI, and the            identified HARQ process is configured for a configured            uplink grant:            -   3> start or restart the configuredGrantTimer for the                correponding HARQ process, if configured.        -   2> deliver the uplink grant and the associated HARQ            information to the HARQ entity.    -   1> else if an uplink grant for this PDCCH occasion has been        received for this Serving Cell on the PDCCH for the MAC entity's        CS-RNTI:        -   2> if the NDI in the received HARQ information is 1:            -   3> consider the NDI for the corresponding HARQ process                not to have been toggled;            -   3> start or restart the configuredGrantTimer for the                corresponding HARQ process, if configured;            -   3> deliver the uplink grant and the associated HARQ                information to the HARQ entity.        -   2> else if the NDI in the received HARQ information is 0:            -   3> if PDCCH contents indicate configured grant Type 2                deactivation:                -   4> trigger configured uplink grant confirmation.            -   3> else if PDCCH contents indicate configured grant Type                2 activation:                -   4> trigger configured uplink grant confirmation;                -   4> store the uplink grant for this Serving Cell and                    the associated HARQ information as configured uplink                    grant;                -   4> initialise or re-initialise the configured uplink                    grant for this Serving Cell to start in the                    associated PUSCH duration and to recur according to                    rules in clause 5.8.2;                -   4> stop the configuredGrantTimer for the                    corresponding HARQ process, if running;                    For each Serving Cell and each configured uplink                    grant, if configured and activated, the MAC entity                    shall:    -   1> if the PUSCH duration of the configured uplink grant does not        overlap with the PUSCH duration of an uplink grant received on        the PDCCH or in a Random Access Response for this Serving Cell:        -   2> set the HARQ Process ID to the HARQ Process ID associated            with this PUSCH duration;        -   2> if the configuredGrantTimer for the corresponding HARQ            process is not running            -   3> consider the NDI bit for the corresponding HARQ                process to have been toggled;            -   3> deliver the configured uplink grant and the                associated HARQ information to the HARQ entity.                For configured uplink grants, the HARQ Process ID                associated with the first symbol of a UL transmission is                derived from the following equation:

HARQ Process ID=[floor(CURRENT_symbol/periodicity)] modulonrofHARQ-Processes

whereCURRENT_symbol=(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotnumber in the frame×numberOfSymbolsPerSlot+symbol number in the slot),and numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the numberof consecutive slots per frame and the number of consecutive symbols perslot, respectively as specified in TS 38.211 [8].

5.4.2 HARQ Operation 5.4.2.1 HARQ Entity

The MAC entity includes a HARQ entity for each Serving Cell withconfigured uplink (including the case when it is configured withsupplementaryUplink), which maintains a number of parallel HARQprocesses.The number of parallel UL HARQ processes per HARQ entity is specified inTS 38.214 [7].Each HARQ process supports one TB.Each HARQ process is associated with a HARQ process identifier. For ULtransmission with UL grant in RA Response, HARQ process identifier 0 isused.When the MAC entity is configured with pusch-AggregationFactor>1, theparameter pusch-AggregationFactor provides the number of transmissionsof a TB within a bundle of the dynamic grant. After the initialtransmission, pusch-AggregationFactor−1 HARQ retransmissions followwithin a bundle. When the MAC entity is configured with repK>1, theparameter repK provides the number of transmissions of a TB within abundle of the configured uplink grant. After the initial transmission,HARQ retransmissions follow within a bundle. For both dynamic grant andconfigured uplink grant, bundling operation relies on the HARQ entityfor invoking the same HARQ process for each transmission that is part ofthe same bundle. Within a bundle, HARQ retransmissions are triggeredwithout waiting for feedback from previous transmission according topusch-AggregationFactor for a dynamic grant and repK for a configureduplink grant, respectively. Each transmission within a bundle is aseparate uplink grant after the initial uplink grant within a bundle isdelivered to the HARQ entity.For each transmission within a bundle of the dynamic grant, the sequenceof redundancy versions is determined according to clause 6.1.2.1 of TS38.214 [7]. For each transmission within a bundle of the configureduplink grant, the sequence of redundancy versions is determinedaccording to clause 6.1.2.3 of TS 38.214 [7].For each uplink grant, the HARQ entity shall:

-   -   1> identify the HARQ process associated with this grant, and for        each identified HARQ process:        -   2> if the received grant was not addressed to a Temporary            C-RNTI on PDCCH, and the NDI provided in the associated HARQ            information has been toggled compared to the value in the            previous transmission of this TB of this HARQ process; or        -   2> if the uplink grant was received on PDCCH for the C-RNTI            and the HARQ buffer of the identified process is empty; or        -   2> if the uplink grant was received in a Random Access            Response; or        -   2> if the uplink grant was received on PDCCH for the C-RNTI            in ra-Response Window and this PDCCH successfully completed            the Random Access procedure initiated for beam failure            recovery; or        -   2> if the uplink grant is part of a bundle of the configured            uplink grant, and may be used for initial transmission            according to clause 6.1.2.3 of TS 38.214 [7], and if no MAC            PDU has been obtained for this bundle:            -   3> if there is a MAC PDU in the Msg3 buffer and the                uplink grant was received in a Random Access Response;                or:            -   3> if there is a MAC PDU in the Msg3 buffer and the                uplink grant was received on PDCCH for the C-RNTI in                ra-ResponseWindow and this PDCCH successfully completed                the Random Access procedure initiated for beam failure                recovery:                -   4> obtain the MAC PDU to transmit from the Msg3                    buffer.                -   4> if the uplink grant size does not match with size                    of the obtained MAC PDU; and                -   4> if the Random Access procedure was successfully                    completed upon receiving the uplink grant:                -    5> indicate to the Multiplexing and assembly entity                    to include MAC subPDU(s) carrying MAC SDU from the                    obtained MAC PDU in the subsequent uplink                    transmission;                -    5> obtain the MAC PDU to transmit from the                    Multiplexing and assembly entity.            -   3> else:                -   4> obtain the MAC PDU to transmit from the                    Multiplexing and assembly entity, if any;            -   3> if a MAC PDU to transmit has been obtained:                -   4> deliver the MAC PDU and the uplink grant and the                    HARQ information of the TB to the identified HARQ                    process;                -   4> instruct the identified HARQ process to trigger a                    new transmission;                -   4> if the uplink grant is addressed to CS-RNTI; or                -   4> if the uplink grant is a configured uplink grant;                    or                -   4> if the uplink grant is addressed to C-RNTI, and                    the identified HARQ process is configured for a                    configured uplink grant:                -    5> start or restart the configuredGrantTimer, if                    configured, for the corresponding HARQ process when                    the transmission is performed.            -   3> else:                -   4> flush the HARQ buffer of the identified HARQ                    process.        -   2> else (i.e. retransmission):            -   3> if the uplink grant received on PDCCH was addressed                to CS-RNTI and if the HARQ buffer of the identified                process is empty; or            -   3> if the uplink grant is part of a bundle and if no MAC                PDU has been obtained for this bundle; or            -   3> if the uplink grant is part of a bundle of the                configured uplink grant, and the PUSCH duration of the                uplink grant overlaps with a PUSCH duration of another                uplink grant received on the PDCCH or in a Random Access                Response for this Serving Cell:                -   4> ignore the uplink grant.            -   3> else:                -   4> deliver the uplink grant and the HARQ information                    (redundancy version) of the TB to the identified                    HARQ process;                -   4> instruct the identified HARQ process to trigger a                    retransmission;                -   4> if the uplink grant is addressed to CS-RNTI; or                -   4> if the uplink grant is addressed to C-RNTI, and                    the identified HARQ process is configured for a                    configured uplink grant:                -    5> start or restart the configuredGrantTimer, if                    configured, for the corresponding HARQ process when                    the transmission is performed.                    When determining if NDI has been toggled compared to                    the value in the previous transmission the MAC                    entity shall ignore NDI received in all uplink                    grants on PDCCH for its Temporary C-RNTI.

5.4.2.2 HARQ Process

Each HARQ process is associated with a HARQ buffer.New transmissions are performed on the resource and with the MCSindicated on either PDCCH, Random Access Response, or RRC.Retransmissions are performed on the resource and, if provided, with theMCS indicated on PDCCH, or on the same resource and with the same MCS aswas used for last made transmission attempt within a bundle.If the HARQ entity requests a new transmission for a TB, the HARQprocess shall:

-   -   1> store the MAC PDU in the associated HARQ buffer;    -   1> store the uplink grant received from the HARQ entity;    -   1> generate a transmission as described below.        If the HARQ entity requests a retransmission for a TB, the HARQ        process shall:    -   1> store the uplink grant received from the HARQ entity;    -   1> generate a transmission as described below.        To generate a transmission for a TB, the HARQ process shall:    -   1> if the MAC PDU was obtained from the Msg3 buffer; or    -   1> if there is no measurement gap at the time of the        transmission and, in case of retransmission, the retransmission        does not collide with a transmission for a MAC PDU obtained from        the Msg3 buffer:        -   2> instruct the physical layer to generate a transmission            according to the stored uplink grant.

Scheduling Request (SR) is introduced in 3GPP TS 38.321, V15.7.0:

5.4.4 Scheduling Request

The Scheduling Request (SR) is used for requesting UL-SCH resources fornew transmission.The MAC entity may be configured with zero, one, or more SRconfigurations. An SR configuration consists of a set of PUCCH resourcesfor SR across different BWPs and cells. For a logical channel, at mostone PUCCH resource for SR is configured per BWP.Each SR configuration corresponds to one or more logical channels. Eachlogical channel may be mapped to zero or one SR configuration, which isconfigured by RRC. The SR configuration of the logical channel thattriggered the BSR (clause 5.4.5) (if such a configuration exists) isconsidered as corresponding SR configuration for the triggered SR.RRC configures the following parameters for the scheduling requestprocedure:

-   -   sr-ProhibitTimer (per SR configuration);    -   sr-TransMax (per SR configuration).        The following UE variables are used for the scheduling request        procedure:    -   SR_COUNTER (per SR configuration).        If an SR is triggered and there are no other SRs pending        corresponding to the same SR configuration, the MAC entity shall        set the SR_COUNTER of the corresponding SR configuration to 0.        When an SR is triggered, it shall be considered as pending until        it is cancelled. All pending SR(s) triggered prior to the MAC        PDU assembly shall be cancelled and each respective        sr-ProhibitTimer shall be stopped when the MAC PDU is        transmitted and this PDU includes a Long or Short BSR MAC CE        which contains buffer status up to (and including) the last        event that triggered a BSR (see clause 5.4.5) prior to the MAC        PDU assembly. All pending SR(s) shall be cancelled and each        respective sr-ProhibitTimer shall be stopped when the UL        grant(s) can accommodate all pending data available for        transmission.        Only PUCCH resources on a BWP which is active at the time of SR        transmission occasion are considered valid.        As long as at least one SR is pending, the MAC entity shall for        each pending SR:    -   1> if the MAC entity has no valid PUCCH resource configured for        the pending SR:        -   2> initiate a Random Access procedure (see clause 5.1) on            the SpCell and cancel the pending SR.    -   1> else, for the SR configuration corresponding to the pending        SR:        -   2> when the MAC entity has an SR transmission occasion on            the valid PUCCH resource for SR configured; and        -   2> if sr-ProhibitTimer is not running at the time of the SR            transmission occasion; and        -   2> if the PUCCH resource for the SR transmission occasion            does not overlap with a measurement gap; and        -   2> if the PUCCH resource for the SR transmission occasion            does not overlap with a UL-SCH resource:            -   3> if SR_COUNTER<sr-TransMax:                -   4> increment SR_COUNTER by 1;                -   4> instruct the physical layer to signal the SR on                    one valid PUCCH resource for SR;                -   4> start the sr-ProhibitTimer.            -   3> else:                -   4> notify RRC to release PUCCH for all Serving                    Cells;                -   4> notify RRC to release SRS for all Serving Cells;                -   4> clear any configured downlink assignments and                    uplink grants;                -   4> clear any PUSCH resources for semi-persistent CSI                    reporting;                -   4> initiate a Random Access procedure (see clause                    5.1) on the SpCell and cancel all pending SRs.    -   NOTE 1: The selection of which valid PUCCH resource for SR to        signal SR on when the MAC entity has more than one overlapping        valid PUCCH resource for the SR transmission occasion is left to        UE implementation.    -   NOTE 2: If more than one individual SR triggers an instruction        from the MAC entity to the PHY layer to signal the SR on the        same valid PUCCH resource, the SR_COUNTER for the relevant SR        configuration is incremented only once.        The MAC entity may stop, if any, ongoing Random Access procedure        due to a pending SR which has no valid PUCCH resources        configured, which was initiated by MAC entity prior to the MAC        PDU assembly. Such a Random Access procedure may be stopped when        the MAC PDU is transmitted using a UL grant other than a UL        grant provided by Random Access Response, and this PDU includes        a BSR MAC CE which contains buffer status up to (and including)        the last event that triggered a BSR (see clause 5.4.5) prior to        the MAC PDU assembly, or when the UL grant(s) can accommodate        all pending data available for transmission.

Activation and deactivation of Secondary Cells (SCells) are introducedin 3GPP TS 38.321, V15.7.0:

5.9 Activation/Deactivation of SCells

If the MAC entity is configured with one or more SCells, the network mayactivate and deactivate the configured SCells. Upon configuration of anSCell, the SCell is deactivated.The configured SCell(s) is activated and deactivated by:

-   -   receiving the SCell Activation/Deactivation MAC CE described in        clause 6.1.3.10;    -   configuring sCellDeactivationTimer timer per configured SCell        (except the SCell configured with PUCCH, if any): the associated        SCell is deactivated upon its expiry.        The MAC entity shall for each configured SCell:    -   1> if an SCell Activation/Deactivation MAC CE is received        activating the SCell:        -   2> activate the SCell according to the timing defined in TS            38.213 [6]; i.e. apply normal SCell operation including:            -   3>SRS transmissions on the SCell;            -   3> CSI reporting for the SCell;            -   3> PDCCH monitoring on the SCell;            -   3> PDCCH monitoring for the SCell;            -   3> PUCCH transmissions on the SCell, if configured.        -   2> if the SCell was deactivated prior to receiving this            SCell Activation/Deactivation MAC CE:            -   3> activate the DL BWP and UL BWP indicated by                firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id                respectively;        -   2> start or restart the sCellDeactivationTimer associated            with the SCell according to the timing defined in TS 38.213            [6];        -   2> (re-)initialize any suspended configured uplink grants of            configured grant Type 1 associated with this SCell according            to the stored configuration, if any, and to start in the            symbol according to rules in clause 5.8.2;        -   2> trigger PHR according to clause 5.4.6.    -   1> else if an SCell Activation/Deactivation MAC CE is received        deactivating the SCell; or    -   1> if the sCellDeactivationTimer associated with the activated        SCell expires:        -   2> deactivate the SCell according to the timing defined in            TS 38.213 [6];        -   2> stop the sCellDeactivationTimer associated with the            SCell;        -   2> stop the bwp-InactivityTimer associated with the SCell;        -   2> deactivate any active BWP associated with the SCell;        -   2> clear any configured downlink assignment and any            configured uplink grant Type 2 associated with the SCell            respectively;        -   2> clear any PUSCH resource for semi-persistent CSI            reporting associated with the SCell;        -   2> suspend any configured uplink grant Type 1 associated            with the SCell;        -   2> flush all HARQ buffers associated with the SCell.    -   1> if PDCCH on the activated SCell indicates an uplink grant or        downlink assignment; or    -   1> if PDCCH on the Serving Cell scheduling the activated SCell        indicates an uplink grant or a downlink assignment for the        activated SCell; or    -   1> if a MAC PDU is transmitted in a configured uplink grant or        received in a configured downlink assignment:        -   2> restart the sCellDeactivationTimer associated with the            SCell.    -   1> if the SCell is deactivated:        -   2> not transmit SRS on the SCell;        -   2> not report CSI for the SCell;        -   2> not transmit on UL-SCH on the SCell;        -   2> not transmit on RACH on the SCell;        -   2> not monitor the PDCCH on the SCell;        -   2> not monitor the PDCCH for the SCell;        -   2> not transmit PUCCH on the SCell.            HARQ feedback for the MAC PDU containing SCell            Activation/Deactivation MAC CE shall not be impacted by            PCell, PSCell and PUCCH SCell interruptions due to SCell            activation/deactivation in TS 38.133 [11].            When SCell is deactivated, the ongoing Random Access            procedure on the SCell, if any, is aborted.

In a Change request for 3GPP TS 38.321, procedure for beam failureprocedure for a SCell is introduced in R2-1915254:

5.17 Beam Failure Detection and Recovery Procedure

The MAC entity may be configured by RRC per Serving Cell with a beamfailure recovery procedure which is used for indicating to the servinggNB of a new SSB or CSI-RS when beam failure is detected on the servingSSB(s)/CSI-RS(s). Beam failure is detected by counting beam failureinstance indication from the lower layers to the MAC entity. IfbeamFailureRecoveryConfig is reconfigured by upper layers during anongoing Random Access procedure for beam failure recovery for SpCell,the MAC entity shall stop the ongoing Random Access procedure andinitiate a Random Access procedure using the new configuration.RRC configures the following parameters in the BeamFailureRecoveryConfigand the RadioLinkMonitoringConfig for the Beam Failure Detection andRecovery procedure:

-   -   beamFailureInstanceMaxCount for the beam failure detection;    -   beamFailureDetectionTimer for the beam failure detection;    -   beamFailureRecoveryTimer for the beam failure recovery        procedure;    -   rsrp-ThresholdSSB: an RSRP threshold for the beam failure        recovery;    -   powerRampingStep: powerRampingStep for the beam failure        recovery;    -   powerRampingStepHighPriority: powerRampingStepHighPriority for        the beam failure recovery;    -   preambleReceivedTargetPower: preambleReceivedTargetPower for the        beam failure recovery;    -   preambleTransMax: preambleTransMax for the beam failure        recovery;    -   scalingFactorBI: scalingFactorBI for the beam failure recovery;    -   ssb-perRACH-Occasion: ssb-perRACH-Occasion for the beam failure        recovery;    -   ra-ResponseWindow: the time window to monitor response(s) for        the beam failure recovery using contention-free Random Access        Preamble;    -   prach-ConfigurationIndex: prach-ConfigurationIndex for the beam        failure recovery;    -   ra-ssb-OccasionMaskIndex: ra-ssb-OccasionMaskIndex for the beam        failure recovery;    -   ra-OccasionList: ra-OccasionList for the beam failure recovery.

Editors Note: The specific parameters for SCell BFR will be replicatedhere after they are settled.

The following UE variables are used for the beam failure detectionprocedure:

-   -   BFI_COUNTER: counter for beam failure instance indication which        is initially set to 0.        The MAC entity shall for each Serving Cell configured for beam        failure detection:    -   1> if beam failure instance indication has been received from        lower layers:        -   2> start or restart the beamFailureDetectionTimer;        -   2> increment BFI_COUNTER by 1;        -   2> if BFI_COUNTER>=beamFailureInstanceMaxCount:            -   3> if the Serving Cell is SCell:                -   4> trigger BFR;            -   3> else:                -   4> initiate a Random Access procedure (see clause                    5.1) on the SpCell.    -   1> if the beamFailureDetectionTimer expires; or    -   1> if beamFailureDetectionTimer, beamFailureInstanceMaxCount, or        any of the reference signals used for beam failure detection is        reconfigured by upper layers associated with this Serving Cell:        -   2> set BFI_COUNTER to 0.    -   1> if the Serving Cell is SpCell and the Random Access procedure        is successfully completed (see clause 5.1):        -   2> set BFI_COUNTER to 0;        -   2> stop the beamFailureRecoveryTimer, if configured;        -   2> consider the Beam Failure Recovery procedure successfully            completed.    -   1> else if the Serving Cell is SCell; and    -   1> if a PDCCH addressed to C-RNTI indicating uplink grant for a        new transmission is received for the HARQ process used for the        SCell BFR MAC CE transmission indicating this Serving Cell:        -   2> set BFI_COUNTER to 0;    -   2> consider the Beam Failure Recovery procedure successfully        completed and cancel all the triggered BFRs for this Serving        Cell.        The MAC entity shall:    -   1> if the Beam Failure Recovery procedure determines that at        least one BFR has been triggered and not cancelled:        -   2> if UL-SCH resources are available for a new transmission            and the UL-SCH resources can accommodate the SCell BFR MAC            CE plus its subheader as a result of logical channel            prioritization:            -   3> instruct the Multiplexing and Assembly procedure to                generate the SCell BFR MAC CE.        -   2> else:            -   3> trigger a Scheduling Request for SCell beam failure                recovery.

6.1.3.XX SCell BFR MAC CE

The SCell BFR MAC CE is identified by a MAC subheader with LCID asspecified in Table 6.2.1-2. It has variable size and consists of thefollowing fields:

Editors Note: Exact fields and format are FFS.

When the SCell BFR MAC CE is to be generated, the MAC entity shall foreach Serving Cell to be reported in this SCell BFR MAC CE:

-   -   1> if at least one of the SSBs with SS-RSRP above        [rsrp-ThresholdSSB] amongst the SSBs in [candidateBeamRSList] or        the CSI-RSs with CSI-RSRP above [rsrp-ThresholdCSI-RS] amongst        the CSI-RSs in [candidateBeamRSList] is available:        -   2> select an SSB with SS-RSRP above [rsrp-ThresholdSSB]            amongst the SSBs in [candidateBeamRSList] or a CSI-RS with            CSI-RSRP above [rsrp-ThresholdCSI-RS] amongst the CSI-RSs in            [candidateBeamRSList];        -   2> set the [new candidate RS field name] to 1 and set the            [new candidate RS index field name] corresponding to the            selected SSB or CSI-RS in the SCell BFR MAC CE.    -   1> else:        -   2> set the [new candidate RS field name] to 0 in the SCell            BFR MAC CE.

Editors Note: The highlighted field names will be changed to the onesdefined for the purpose.

In 3GPP RAN2 #107bis meeting, agreements associated with BFR procedurefor SCell have been made, at least some of which are quoted below from3GPP RAN2 #107bis meeting report:

Agreements: 1. The Scell beam failure detection is per cell. 2. Each DLBWP of a SCell can be configured with an independent SCell BFRconfiguration (the content is FFS) 3. One SR ID is configured for BFRwithin the same cell group. 4. The SCell BFRQ MAC CE triggers a SCellBFRQ SR if there is no valid uplink grant which can accommodate theSCell BFRQ MAC CE. 5. FFS whether the transmission of the SCell BFRQ MACCE cancels the pending BFRQ SR of the failed SCell(s).(depends whetherthe MAC CE provides info for one or more Scells) 6. When the number ofthe BFRQ SR transmission reaches the sr-TransMax, the UE triggers a RACHprocedure (i.e. reuse Rel-15 behaviour)

Discussion of a BFR procedure is quoted below from a document,R1-1909833, associated with a 3GPP RAN1 #98 meeting:

Q1: Can the UE transmit BFR MAC CE using UL grant of any serving cell orshould there be a restriction not to send it on failed serving cell(s)?R1: At least from RAN1 perspective, there is no need for introducingsuch restrictions on MAC CE transmission for BFR in Rel-16.Q2: If the UE already has the UL grant on serving cell(s) on which BFRMAC CE can be transmitted based on the answer to question 1, is the UEstill required to transmit SR-like indication for BFR?R2: In this case, UE is not required to transmit SR-like indication forSCell BFR.Q3: Is there a case where the SR-like dedicated PUCCH resource for SCellBFR is not configured? If the SR-like dedicated PUCCH resource is notconfigured, one possible option being considered by RAN2 is that the UEfollows the existing framework for requesting uplink resources when nouplink resources are available (i.e. performs CBRA on SpCell).R3: RAN1 did not discuss this case. RAN1 plans to conclude on this byRAN1 #98bis.Q4: Is the SR-like dedicated PUCCH resource for SCell BFR configured foreach SCell separately or is it common for all SCell(s) of the same cellgroup (i.e. MCG/SCG)?R4: The SR-like dedicated PUCCH resource for SCell BFR is not configuredseparately for each SCell.Q5: What conditions are used for the (successful) completion of theSCell BFR?R5: When UE receives beam failure recovery response (BFRR) to step 2, UEcan consider BFR procedure is finished, where the BFRR to step 2 is anormal uplink grant to schedule a new transmission for the same HARQprocess as PUSCH carrying the step 2 MAC CE, which is the same as normal“ACK” for PUSCH.

In 3GPP RAN2 #108 meeting, agreements associated with BFR procedure forSCell have been made, at least some of which are quoted below from 3GPPRAN2 #108 meeting report:

Agreements: 1. beamFailureDetectionTimer and beamFailurelnstanceMaxCountare configured cell specifically per each DL BWP configured. 2. Uponreconfiguration of beamFailureDetectionTimer,beamFailurelnstanceMaxCount, or any of the reference signals used forbeam failure detection by upper layers, BFI_COUNTER is set to 0 for thegiven Serving Cell. 3. When SCell BFR SR resource is not configured andSCell BFR MAC CE transmission triggers SCell BFR SR, Random Accessprocedure on SpCell is triggered to request UL resources to transmit theSCell BFR MAC CE (similarly to Rel-15 behaviour on SR). 4. when SCellBFR SR is triggered and the UE has an overlapping SR PUCCH resource withthe SCell BFR SR PUCCH resource, the UE shall select the SCell BFR SRPUCCH resource for transmission. 5. Pending SR for SCell beam failurerecovery triggered prior to the MAC PDU assembly shall be cancelled whenthe MAC PDU is transmitted and this PDU includes a SCell BFR MAC CE. 6.SCell BFR MAC CE can carry information of multiple failed SCells, ie.,multiple entry format for SCell BFR MAC CE is defined. 7. For eachSCell, the SCell BFR MAC CE indicates the following information: information about the failed SCell index;  indication if a newcandidate beam RS is detected or not;  new candidate beam RS index (ifavailable). 8. SCell BFR MAC CE has higher priority at least than “datafrom any Logical Channel, except data from UL-CCCH” and LBT MAC CE,higher priority is FFS.

In NR, beam failure recovery (BFR) and BFR procedure for a Secondarycell (SCell) has been introduced. A UE may trigger a BFR (e.g. a triggerfor generating a BFR MAC CE (e.g., a SCell BFR MAC CE) or a trigger fortriggering a Scheduling Request (SR) for SCell beam failure recovery) inresponse to receiving one or more beam failure indications (e.g.,consecutive beam failure indications) from one or more lower layers(e.g., a physical layer) of the UE. For example, the UE may trigger theBFR in response to receiving consecutive beam failure indications,amounting to a threshold number of beam failure indications, from theone or more lower layers of the UE. The UE may perform a BFR procedurein response to the one or more beam failure indications from the one ormore lower layers. In some examples, a BFR procedure for a SCell maycomprise transmission of a Scheduling Request (SR) to a base station(e.g., the SR may be transmitted to the base station to request one ormore uplink (UL) resources for transmitting a MAC control element (CE)).Alternatively and/or additionally, the BFR procedure may comprisetransmission of a MAC CE (e.g., a BFR MAC CE), using a Hybrid AutomaticRepeat Request (HARQ) process, to the base station (e.g., the MAC CE maybe transmitted during the HARQ process and/or the MAC CE may betransmitted by performing one or more operations of the HARQ process).In some examples, the MAC CE may indicate one or more candidate beamsassociated with BFR. Alternatively and/or additionally, the MAC CE mayindicate one or more SCells associated with a triggered BFR (e.g., theBFR triggered in response to receiving the one or more beam failureindications) and/or the ongoing BFR procedure. The UE may consider theBFR procedure to be finished and/or completed when the base stationschedules an UL grant for a transmission (e.g., a new transmission forthe same HARQ process used to transmit the MAC CE).

An issue, such as illustrated in FIG. 5, may occur when a cell,associated with a triggered BFR (e.g. a trigger for generating a BFR MACCE (e.g., a SCell BFR MAC CE) or a trigger for triggering a SR for SCellbeam failure recovery) and/or an ongoing BFR procedure, is deactivatedbefore the triggered BFR is canceled and/or the ongoing BFR procedure isfinished. FIG. 5 illustrates an exemplary scenario 500 associated with atriggered BFR, according to some embodiments. In the exemplary scenario500, a UE is configured with multiple cells (e.g., two cells), Cell 1and Cell 2, by a base station. Cell 1 may be a Primary Cell (PCell) or aSCell. Cell 2 may be a SCell. The UE is configured with a timer (e.g.,sCellDeactivationTimer) associated with Cell 2 (e.g., the timer is shownas “sCellDeactivationTimer For Cell 2” in FIG. 5). At a timing t1, theUE may trigger BFR associated with Cell 2 (e.g., the UE may trigger BFRassociated with Cell 2 in response to one or more beam failureindications from one or more lower layers of the UE). The UE may performa BFR procedure in response to the triggered BFR (and/or in response tothe triggered BFR being triggered by the UE). At a timing t2, the UEtransmits a SR in response to the triggered BFR on Cell 1 (e.g., inresponse to BFR on Cell 1 being triggered by the UE). The UE may beconfigured with one or more SR resources (e.g., one or more PhysicalUplink Control Channel (PUCCH) resources) on Cell 1 (e.g., the one ormore SR resources may correspond to one or more resources fortransmission of one or more SRs to the base station). In an example, theUE may use the one or more SR resources to transmit the SR to the basestation. At a timing t3, in response to the SR, the base station mayindicate a first UL grant (shown as “UL grant 1” in FIG. 5), on Cell 1,for new transmission. The UE may receive the first UL grant “UL grant 1”and/or use the first UL grant “UL grant 1” to transmit, at a timing t4,a MAC CE (e.g., a BFR MAC CE) using a HARQ process (e.g., HARQ process1) indicating information associated with BFR for Cell 2. At a timingt5, the base station may indicate a second UL grant (shown as “UL grant2” in FIG. 5) for new transmission for the HARQ process (e.g., the HARQprocess 1 used to transmit the MAC CE) to finish the BFR procedure.However, at a timing t6, the timer (e.g., sCellDeactivationTimer) mayexpire before completion of the BFR procedure (e.g., the timer mayexpire before the completion of the BFR procedure since the UE may notbe able to receive downlink (DL) signaling from Cell 2) and/or Cell 2may be deactivated (e.g., Cell 2 may be deactivated in response toexpiration of the timer). The ongoing BFR procedure may incurunnecessary transmission overhead between the UE and the base stationsince the BFR procedure is for recovery of transmission between Cell 2and the UE and/or since the BFR procedure may be unnecessary if Cell 2is deactivated. The transmission of the MAC CE (e.g., the BFR MAC CE)may be outdated and may cause the base station to schedule anunnecessary UL grant (e.g., the second UL grant “UL grant 2”), such asfor performance of the BFR procedure. In some examples, if the UE is notconfigured with a SR configuration for BFR for Cell 2, the UE maytrigger a random access procedure in response to the triggered BFR, andthe random access procedure may interfere with connection establishmentof other UEs to the base station.

To solve the foregoing issues, such as to avoid unnecessarily performingoperations of a BFR procedure, the present disclosure provides for oneor more techniques, systems and/or operations with respect to ExampleEmbodiment 1 and Example Embodiment 2.

Example Embodiment 1

In Example Embodiment 1, a UE may cancel one or more triggered BFRsassociated with a cell in response to a deactivation of the cell. Forexample, the UE may cancel a first triggered BFR associated with a firstcell in response to deactivation of the first cell. Alternatively and/oradditionally, the UE may stop an ongoing BFR procedure associated withthe first cell in response to the deactivation of the first cell.Alternatively and/or additionally, the UE may stop the ongoing BFRprocedure associated with the first cell, in response to thedeactivation of the first cell, if a BFR MAC CE generated in response tothe ongoing BFR procedure comprises beam failure information of only thefirst cell (and/or if the BFR MAC CE generated in response to theongoing BFR procedure does not report beam failure of any cell that isactivated for the UE).

Alternatively and/or additionally, the UE may stop the ongoing BFRprocedure associated with the first cell, in response to thedeactivation of the first cell, if the UE does not have one or moreother cells (e.g., one or more activated cells) associated with atriggered and/or pending BFR (e.g., a second triggered BFR other thanthe first triggered BFR). For example, the UE may stop the ongoing BFRprocedure associated with the first cell, in response to thedeactivation of the first cell, if the UE is not configured with a cell(e.g., any cell) that is activated and is associated with a triggeredand/or pending BFR. Alternatively and/or additionally, UE may stop theongoing BFR procedure (such as in response to deactivation of the firstcell) if beam failure information, indicated in a BFR MAC CE generatedin response to the ongoing BFR procedure, does not comprise beam failureinformation of one or more activated cells (e.g., since the first cellis deactivated, the first cell may not be considered when determiningwhether or not the beam failure information indicated in the BFR MAC CEcomprises beam failure information of one or more activated cells). Insome examples, the UE may not stop a BFR procedure (such as the ongoingBFR procedure) if there is at least one activated cell (with which theUE is configured) that is associated with a triggered and/or pendingBFR. The UE may not stop a BFR procedure (such as the ongoing BFRprocedure) if a BFR MAC CE generated in response to the BFR procedurecomprises beam failure information of at least one activated cell (thatis different than the first cell, for example, since the first cell isdeactivated).

The ongoing BFR procedure may comprise transmission of a SR or a SRtransmission for BFR (e.g., a SR for SCell beam failure recoveryassociated with the first triggered BFR). For example, the SR (e.g., theSR for SCell beam failure recovery) may be transmitted to a base stationto request one or more UL resources for transmission of a MAC CE (e.g.,a BFR MAC CE of the ongoing BFR procedure). The UE may trigger the SR(e.g. a trigger for SR transmission or for initiating a random accessprocedure) in response to the first triggered BFR (e.g., the UE maytrigger and/or transmit the SR in response to the first triggered BFRbeing triggered). Alternatively and/or additionally, the UE may stoptransmission of the SR, in response to deactivation of the first cell,if the UE does not have one or more other cells (e.g., one or moreactivated cells) associated with a triggered and/or pending BFR (e.g., asecond triggered BFR other than the first triggered BFR). For example,the UE may stop transmission of the SR or the SR transmission, inresponse to the deactivation of the first cell, if the UE is notconfigured with a cell (e.g., any cell) that is activated and isassociated with a triggered and/or pending BFR. The UE may not stoptransmission of the SR or the SR transmission (such as in response todeactivation of the first cell) if there is at least one activated cell(with which the UE is configured) associated with a triggered and/orpending BFR (e.g., second triggered BFR other than the first triggeredBFR).

In some examples, prior to the UE stopping transmission of the SR or aSR transmission (e.g., the SR triggered in response to the firsttriggered BFR), the UE may perform one or more transmissions of the SR(e.g., the UE may transmit the SR to a base station one or more timesprior to the deactivation of the first cell and/or prior to the UEstopping transmission of the SR or a SR transmission).

In an example, the UE may not stop transmission of a SR or a SRtransmission associated with BFR if there is at least one activated cellassociated with a triggered BFR (e.g., the UE may not stop transmissionof a SR or a SR transmission associated with BFR if at least one cell,with which the UE is configured, is activated and associated with atriggered and/or pending BFR). The UE may stop transmission of a SR or aSR transmission associated with BFR if there are no activated cellsassociated with a triggered BFR (e.g., the UE may stop transmission of aSR or a SR transmission associated with BFR if there are no cells, withwhich the UE is configured, that are activated and associated with atriggered and/or pending BFR).

In another example, the UE may not stop transmission of a BFR MAC CEassociated with BFR if there is at least one activated cell associatedwith a triggered BFR (e.g., the UE may not stop transmission of a BFRMAC CE associated with BFR if at least one cell, with which the UE isconfigured, is activated and associated with a triggered and/or pendingBFR). The UE may stop transmission of a BFR MAC CE associated with BFRif there are no activated cells associated with a triggered BFR (e.g.,the UE may stop transmission of a BFR MAC CE associated with BFR ifthere are no cells, with which the UE is configured, that are activatedand associated with a triggered and/or pending BFR).

Alternatively and/or additionally, the UE may cancel a triggered SR(e.g. a trigger for SR transmission or a trigger for initiating a randomaccess procedure) for BFR (e.g., SCell beam failure recovery) associatedwith the first cell in response to the deactivation of the first celland/or in response to stopping the ongoing BFR procedure.

Alternatively and/or additionally, in response to the deactivation ofthe first cell and/or in response to stopping the ongoing BFR procedure,the UE may stop a random access procedure initiated in response to a SRor BFR triggered for the first cell (e.g., the UE may stop any ongoingrandom access procedure that is initiated in response to a SR or BFRtriggered for the first cell).

Alternatively and/or additionally, the UE may not transmit a BFR MAC CEthat is generated before deactivation of the first cell. The BFR MAC CEmay indicate beam failure information of the first cell.

Alternatively and/or additionally, the UE may discard a BFR MAC CEassociated with the first triggered BFR (e.g., the UE may discard theBFR MAC CE in response to the deactivation of the first cell).Alternatively and/or additionally, the UE may generate a MAC PDU withoutthe BFR MAC CE (e.g., a MAC PDU that does not comprise the BFR MAC CE).Alternatively and/or additionally, the UE may rebuild a first MAC PDUcomprising the BFR MAC CE to a second MAC PDU without the BFR MAC CE(e.g., the second MAC PDU does not comprise the BFR MAC CE). Forexample, the second MAC PDU may be generated based upon the first MACPDU (e.g., the second MAC PDU may comprise information, of the first MACPDU, other than the BFR MAC CE). Alternatively and/or additionally, thefirst MAC PDU may be modified to generate the second MAC PDU (e.g., thefirst MAC PDU may be modified by removing the BFR MAC CE to generate thesecond MAC PDU).

Alternatively and/or additionally, the UE may not discard the BFR MAC CEassociated with the first triggered BFR if the BFR MAC CE indicates beamfailure of one or more other cells that are not associated with adeactivation. For example, the UE may not discard the BFR MAC CEassociated with the first triggered BFR if the BFR MAC CE comprises beamfailure information of one or more activated cells.

Alternatively and/or additionally, the UE may not cancel a triggered BFRthat is not associated with a deactivated cell (e.g., a triggered BFRthat is associated with an activated cell).

Alternatively and/or additionally, the UE may not stop a BFR procedure(e.g., an ongoing BFR procedure) associated with one or more cells(e.g., one or more activated cells) other than the first cell.

FIG. 6 illustrates an exemplary scenario 600 associated with a triggeredBFR, according to some embodiments. In the exemplary scenario 600, a UEis configured with multiple serving cells (e.g., two activated servingcells), Cell 1 and Cell 2. At a timing t1, the UE may trigger thetriggered BFR (for SCell beam failure recovery, for example) associatedwith Cell 2 (e.g., the UE may trigger the triggered BFR in response toone or more beam failure indications associated with Cell 2 from one ormore lower layers). In some examples, the UE performs a BFR procedure inresponse to the triggered BFR. Alternatively and/or additionally, the UEmay trigger a SR in response to the triggered BFR. The UE may transmitthe SR, at a timing t2, to a base station for requesting one or more ULresources. The base station indicates a first UL grant (shown as “ULgrant 1” in FIG. 6) at a timing t3 via PDCCH (e.g., the first UL grantmay be received by the UE, at the timing t3, via PDCCH). The UE isconfigured with a timer (e.g., sCellDeactivationTimer) associated withCell 2 (e.g., the timer is shown as “sCellDeactivationTimer For Cell 2”in FIG. 6). The timer may expire at a timing t6. In response toexpiration of the timer (e.g., sCellDeactivationTimer), the UE maydeactivate Cell 2 and/or stop the BFR procedure. The UE does nottransmit, to the base station, a BFR MAC CE indicating beam failure ofCell 2. For example, the first UL grant “UL grant 1” may indicate one ormore UL resources for transmission of the BFR MAC CE at a timing t4(e.g., the UE may use the first UL grant “UL grant 1” to transmit theBFR MAC CE at the timing t4 using a HARQ process). The UE may nottransmit the BFR MAC CE at the timing t4 in response to expiration ofthe timer before the timing t4 (and/or the UE may not transmit the BFRMAC CE at the timing t4 in response to deactivation of Cell 2).

In some examples, the timer may expire before transmission of the SR(e.g., the timing t6 corresponding to the expiration of the timer may bebefore the timing t2 corresponding to transmission of the SR). In someexamples, the UE does not transmit (and/or does not retransmit) a SRassociated with the triggered BFR of Cell 2 to the base station if thetimer expires. For example, if the timing t6 (corresponding to theexpiration of the timer) is before the timing t2 (corresponding totransmission of the SR), the SR associated with the triggered BFR ofCell 2 may not be transmitted (and/or retransmitted) to the basestation.

Alternatively and/or additionally, the UE may not generate a BFR MAC CEin response to a triggered BFR if the timer (e.g.,sCellDeactivationTimer) expires after the triggered BFR is triggered.

Example Embodiment 2

In Example Embodiment 2, a UE may trigger a BFR and/or generate a BFRMAC CE, when a BFR procedure is ongoing, in response to deactivation ofa cell.

In some examples, a UE transmits a first BFR MAC CE associated with atriggered BFR for a first cell. The UE may generate a second BFR MAC CEin response to deactivation associated with the first cell (e.g.,deactivation of the first cell). The second BFR MAC CE may not indicatebeam failure of one or more deactivated cells (e.g., the second BFR MACCE may not indicate beam failure of the first cell based upon thedeactivation of the first cell). The first BFR MAC CE may comprise beamfailure information of multiple cells (e.g., the multiple cells maycomprise the first cell and one or more other cells). In some examples,the first cell is deactivated after transmission (and/or generation) ofthe first BFR MAC CE (e.g., the first BFR MAC CE may indicate beamfailure of the first cell due to the first cell being activated (and notdeactivated) when the first BFR MAC CE is transmitted and/or generated).The UE may cancel a triggered BFR associated with one or moredeactivated cells of the multiple cells (e.g., the one or moredeactivated cells comprise the first cell). In some examples, the UEdoes not stop a BFR procedure associated with the one or moredeactivated cells if the UE generates a BFR MAC CE (e.g., the first BFRMAC CE) in response to the BFR procedure and the BFR MAC CE comprisesbeam failure information of one or more cells (of the multiple cells)that are not deactivated. In some examples, the UE may not generate thesecond BFR MAC CE if the BFR procedure is complete (such as if the BFRprocedure is completed before the first cell is deactivated for the UE).The UE may generate the second BFR MAC CE if the BFR procedure is notcomplete. For example, in response to deactivation of the first cell,the UE may generate the second BFR MAC CE if the BFR procedure is notcomplete (and/or if the multiple cells comprise one or more cells thatare activated for the UE after the first cell is deactivated for theUE).

In some examples, the UE may discard the first BFR MAC CE (in responseto deactivation of the first cell, for example). Alternatively and/oradditionally, the UE may generate a MAC PDU that comprises the secondBFR MAC CE and does not comprise the first BFR MAC CE. Alternativelyand/or additionally, the UE may rebuild a first MAC PDU comprising thefirst BFR MAC CE to a second MAC PDU that comprises the second BFR MACCE and does not comprise the first BFR MAC CE. For example, the secondMAC PDU may be generated based upon the first MAC PDU (e.g., the secondMAC PDU may comprise information, of the first MAC PDU, other than thefirst BFR MAC CE). Alternatively and/or additionally, the first MAC PDUmay be modified to generate the second MAC PDU (e.g., the first MAC PDUmay be modified by removing the first BFR MAC CE and adding the secondBFR MAC CE to generate the second MAC PDU).

FIG. 7 illustrates an exemplary scenario 700 associated with a triggeredBFR, according to some embodiments. In the exemplary scenario 700, a UEis configured with multiple serving cells (e.g., three activated servingcells), Cell 1, Cell 2 and Cell 3. A UE triggers one or more BFRsassociated with Cell 2 and Cell 3 at (and/or before) a timing t1 (e.g.,the UE may trigger the one or more BFRs associated with Cell 2 and Cell3 in response to one or more beam failure indications from lowerlayers). The one or more BFRs may comprise a first triggered BFRassociated with Cell 2 and a second triggered BFR associated with Cell3. In some examples, the UE performs a BFR procedure in response to theone or more BFRs associated with Cell 2 and Cell 3 (e.g., the BFRprocedure may be performed in response to triggering the one or moreBFRs). The UE may transmit a SR, at a timing t2, to a base station forrequesting one or more UL resources. The base station indicates a firstUL grant (shown as “UL grant 1” in FIG. 7) at a timing t3 via PDCCH(e.g., the first UL grant may be received by the UE, at the timing t3,via PDCCH). The UE may generate a first MAC CE (e.g., a first BFR MACCE) associated with the one or more BFRs based upon the UL grant. At atiming t4, the UE may transmit the first MAC CE to the base station(e.g., the UE may transmit the first MAC CE using one or more ULresources of the first UL grant “UL grant 1”). The UE is configured witha timer (e.g., sCellDeactivationTimer) associated with Cell 2 (e.g., thetimer is shown as “sCellDeactivationTimer For Cell 2” in FIG. 7). Thetimer may expire at a timing t5. In response to expiration of the timer(e.g., sCellDeactivationTimer), the UE may deactivate Cell 2. Inresponse to expiration of the timer (e.g., sCellDeactivationTimer)and/or in response to deactivation of Cell 2, the UE may generate asecond MAC CE (e.g., a second BFR MAC CE). The second MAC CE maycomprise beam failure information of Cell 3 (e.g., the UE may generatethe second MAC CE that comprises the beam failure information of Cell 3based upon a determination that Cell 3 is not deactivated when the UEgenerates the second MAC CE). The second MAC CE may not comprise beamfailure information of Cell 2 (e.g., the UE may generate the second MACCE that does not comprise beam failure information of Cell 2 based upona determination that Cell 2 is deactivated). At a timing t6, the UE maytransmit the second MAC CE to the base station.

The first MAC CE may be transmitted on a cell of the multiple cells(e.g., at least one of Cell 1, Cell 2, Cell 3, etc.).

The second MAC CE may be transmitted on a cell of the multiple cells(e.g., at least one of Cell 1, Cell 2, Cell 3, etc.).

The first MAC CE may be transmitted on a cell that is different from acell on which the second MAC CE is transmitted. Alternatively and/oradditionally, the first MAC CE may be transmitted on a cell that is thesame as a cell on which the second MAC CE is transmitted. For example,as shown in FIG. 7, both the first MAC CE and the second MAC CE may betransmitted on Cell 1.

In some examples, the UE may not generate the second MAC CE if cells(e.g., all cells), that are associated with beam failure informationindicated in the first MAC CE, are deactivated. For example, the UE maynot generate the second MAC CE if cells (e.g., all cells), for whichbeam failure is indicated by the first MAC CE, are deactivated.

FIG. 8 illustrates an exemplary scenario 800 associated with a triggeredBFR, according to some embodiments. In the exemplary scenario 800, a UEis configured with multiple serving cells (e.g., three activated servingcells), Cell 1, Cell 2 and Cell 3. The multiple serving cells may beactivated before a timing t1. A UE triggers one or more BFRs associatedwith Cell 2 and Cell 3 at (and/or before) the timing t1 (e.g., the UEmay trigger the one or more BFRs associated with Cell 2 and Cell 3 inresponse to receiving one or more beam failure indications). The one ormore BFRs may comprise a first triggered BFR associated with Cell 2 anda second triggered BFR associated with Cell 3. In some examples, the UEperforms a BFR procedure in response to receiving the one or more beamfailure indications and/or in response to the one or more BFRsassociated with Cell 2 and Cell 3 (e.g., the BFR procedure may beperformed in response to triggering the one or more BFRs). The UE maygenerate a first BFR MAC CE. The UE may transmit, at a timing t2, thefirst BFR MAC CE to a base station on Cell 2. The UE may use aconfigured grant on Cell 2 to transmit the first BFR MAC CE (e.g., theconfigured grant may correspond to one or more resources, on Cell 2,that the UE can use for transmission of the first BFR MAC CE). The firstBFR MAC CE may comprise beam failure information of Cell 2 and Cell 3.The base station may transmit, to the UE, a SCell deactivation MAC CEfor deactivating Cell 2 (e.g., the SCell deactivation MAC CE may be aMAC CE that indicates and/or instructs deactivation of Cell 2). The UEmay receive the SCell deactivation MAC CE at a timing t3. Cell 2 may bedeactivated in response to the SCell deactivation MAC CE. In response todeactivation of Cell 2, the UE may generate a second BFR MAC CE. Thesecond BFR MAC CE may comprise beam failure information of Cell 3 (e.g.,the UE may generate the second BFR MAC CE that comprises the beamfailure information of Cell 3 based upon a determination that Cell 3 isactivated (and/or not deactivated) when the UE generates the second BFRMAC CE). The second BFR MAC CE may not comprise beam failure informationof Cell 2 (e.g., the UE may generate the second BFR MAC CE that does notcomprise beam failure information of Cell 2 based upon a determinationthat Cell 2 is deactivated). At a timing t6, the UE may transmit thesecond BFR MAC CE on Cell 1. In some examples, in response todeactivation of Cell 2, the UE may not stop the BFR procedure based uponCell 3 not being deactivated (and/or based upon Cell 3 being activated).For example, the UE may not stop the BFR procedure based upon at leastone cell, of one or more cells reported and/or indicated by the firstBFR MAC CE, not being deactivated (e.g., at least one cell of the one ormore cells is activated). The one or more cells reported in and/orindicated by the first BFR MAC CE may correspond to one or more cellsfor which beam failure information is included in the first BFR MAC CE(e.g., the one or more cells may comprise Cell 2 and Cell 3).Alternatively and/or additionally, the UE may stop the BFR procedure ifthe one or more cells reported in and/or indicated by the first BFR MACCE are all deactivated (e.g., if both Cell 2 and Cell 3 aredeactivated).

With respect to one or more embodiments herein, in some examples, a cell(e.g., at least one of a cell, a first cell, Cell 1, Cell 2, Cell 3,etc. discussed in one or more example embodiments herein) may be aSCell. Alternatively and/or additionally, a cell may be a PCell and/or aServing Cell.

With respect to one or more embodiments herein, in some examples, adeactivation of a cell may be in response to a SCellActivation/Deactivation MAC CE from a base station (e.g., the UE maydeactivate the cell in response to receiving the SCellActivation/Deactivation MAC CE). For example, the SCellActivation/Deactivation MAC CE (e.g., a SCell Deactivation MAC CE) mayindicate (and/or may be for) deactivation of the cell.

With respect to one or more embodiments herein, in some examples, adeactivation of a cell may be in response to a MAC CE transmitted by abase station (e.g., the UE may deactivate the cell in response toreceiving the MAC CE).

With respect to one or more embodiments herein, in some examples, adeactivation of a cell may be in response to expiration of a timer. Insome examples, the timer is sCellDeactivationTimer associated with thecell.

With respect to one or more embodiments herein, in some examples, atriggered BFR may be considered to be pending before the triggered BFRis canceled (or completed).

With respect to one or more embodiments herein, in some examples, the UEmay be configured with multiple Serving Cells.

With respect to one or more embodiments herein, in some examples, beamfailure information is associated with one or more cells associated withbeam failure. The beam failure information may comprise one or more cellidentities indicative of the one or more cells associated with beamfailure. For example, beam failure of the one or more cells may bereported via the one or more cell identities of the beam failureinformation.

With respect to one or more embodiments herein, in some examples, beamfailure information is indicative of one or more candidate beamsassociated with one or more cells.

With respect to one or more embodiments herein, in some examples, beamfailure information indicates presence of one or more candidate beams(e.g., the beam failure information may indicate whether or not one ormore candidate beams are present and/or available).

With respect to one or more embodiments herein, in some examples, a BFRMAC CE (e.g., a MAC CE for BFR) may comprise beam failure information ofone cell.

With respect to one or more embodiments herein, in some examples, a BFRMAC CE (e.g., a MAC CE for BFR) may comprise beam failure information ofmultiple cells.

With respect to one or more embodiments herein, in some examples, the UEtransmits the BFR MAC CE and/or the SR on a cell different from a cellassociated with a triggered BFR. In some examples, the UE performs theSR transmission on a cell different from a cell associated with atriggered BFR.

With respect to one or more embodiments herein, in some examples, a BFRprocedure may comprise transmission of a SR or a SR transmission (e.g.,a SR associated with a triggered BFR and/or a SR for SCell beam failurerecovery). Alternatively and/or additionally, the BFR procedure may be(and/or may consist of) transmission of a SR or a SR transmission (e.g.,a SR associated with a triggered BFR and/or a SR for SCell beam failurerecovery).

With respect to one or more embodiments herein, in some examples, a BFRprocedure may comprise transmission of a BFR MAC CE indicating beamfailure information associated with one or more cells (e.g., one or morefailed Serving Cells). Alternatively and/or additionally, the BFRprocedure may be (and/or may consist of) transmission of a BFR MAC CEindicating beam failure information associated with one or more cells(e.g., one or more failed Serving Cells).

With respect to one or more embodiments herein, in some examples, a BFRprocedure may be considered to be completed and/or finished when the UEreceives a PDCCH signal indicating an UL grant for a HARQ process usedto transmit a BFR MAC CE associated with the BFR procedure (e.g., the ULgrant may correspond to one or more UL resources that can be used fortransmission of the BFR MAC CE).

With respect to one or more embodiments herein, in some examples, the UEmay generate a BFR MAC CE if a triggered BFR (e.g., a BFR that istriggered, such as at least one of the first triggered BFR, the firstBFR, etc. discussed in one or more example embodiments herein) is notcanceled and if and/or when there are one or more Uplink Shared Channel(UL-SCH) resources available that are for accommodating (and/or that canaccommodate transmission of) the BFR MAC CE and a subheader of the BFRMAC CE (as a result of logical channel prioritization, for example).

With respect to one or more embodiments herein, in some examples, the UEmay trigger a SR for SCell beam failure recovery if a triggered BFR(e.g., a BFR that is triggered, such as at least one of the firsttriggered BFR, the first BFR, etc. discussed in one or more exampleembodiments herein) is not canceled and if no UL-SCH resources areavailable that are for accommodating (and/or that can accommodatetransmission of) a BFR MAC CE and a subheader of the BFR MAC CE (as aresult of logical channel prioritization, for example).

With respect to one or more embodiments herein, in some examples, if anumber of beam failure indications of one or more beam failureindications (e.g., beam failure instance indications) associated with acell (received from one or more lower layers) is larger than or equal toa threshold, and the cell is a SCell, the UE may trigger a BFR (of thecell). The UE may determine whether or not to trigger the BFR based uponwhether the cell is PCell or SCell. For example, the UE may not triggera BFR if the cell is a PCell.

With respect to one or more embodiments herein, in some examples,transmission of the SR or SR transmission is used and/or performed forindicating information to a serving gNB in response to detecting beamfailure on one or more serving Synchronization Signal Blocks (SSBs)and/or one or more serving Channel State Information Reference Signals(CSI-RSs) (and/or transmission of the SR or SR transmission may be usedand/or performed for indicating the information to the serving gNB whenbeam failure on the one or more serving SSBs and/or the one or moreserving CSI-RSs is detected). The information may comprise a new SSB(e.g., a SSB different from the one or more serving SSBs) and/or a newCSI-RS (e.g., a CSI-RS different from the one or more serving CSI-RSs).

With respect to one or more embodiments herein, in some examples, afailed Serving Cell may be a serving cell associated with a triggered(and not canceled) BFR.

One, some and/or all of the foregoing techniques, concepts and/orembodiments can be formed to a new embodiment.

In some examples, embodiments disclosed herein, such as embodimentsdescribed with respect to Example Embodiment 1 and Example Embodiment 2,may be implemented independently and/or separately. Alternatively and/oradditionally, a combination of embodiments described herein, such asembodiments described with respect to Example Embodiment 1 and/orExample Embodiment 2, may be implemented. Alternatively and/oradditionally, a combination of embodiments described herein, such asembodiments described with respect to Example Embodiment 1 and/orExample Embodiment 2, may be implemented concurrently and/orsimultaneously.

Various techniques of the present disclosure may be performedindependently and/or separately from one another. Alternatively and/oradditionally, various techniques of the present disclosure may becombined and/or implemented using a single system. Alternatively and/oradditionally, various techniques of the present disclosure may beimplemented concurrently and/or simultaneously.

FIG. 9 is a flow chart 900 according to one exemplary embodiment fromthe perspective of a UE. In step 905, the UE is configured, by a basestation, with a first cell and a second cell. In step 910, the UEtriggers a first BFR associated with the first cell. In step 915, the UEtriggers a second BFR associated with the second cell. In step 920, theUE generates a first MAC CE in response to the first (triggered) BFRand/or the (triggered) second BFR. In step 925, the UE performs a celldeactivation deactivating the first cell. In step 930, the UE generatesa second MAC CE in response to the cell deactivation. In step 935, theUE transmits the second MAC CE to the base station.

In one embodiment, the UE deactivates the first cell in response to athird MAC CE transmitted by the base station, wherein the third MAC CEindicates deactivation of the first cell.

In one embodiment, the UE deactivates the first cell in response toexpiration of a timer associated with the first cell.

In one embodiment, the UE does not transmit the first MAC CE if (and/orafter) the UE generates the second MAC CE.

In one embodiment, the UE cancels the first (triggered) BFR in responseto the cell deactivation.

In one embodiment, the UE does not stop a BFR procedure associated withthe first (triggered) BFR and the second (triggered) BFR in response tothe cell deactivation (e.g., the UE may not stop the BFR procedure basedupon a determination that the BFR procedure is associated with at leastone cell that is not deactivated, such as the second cell).

In one embodiment, the UE transmits the first MAC CE on the first cell,the second cell, or one or more other activated cells.

In one embodiment, the UE transmits the first MAC CE on a first celldifferent than a second cell on which the UE transmits the second MACCE.

In one embodiment, the UE transmits the first MAC CE and the second MACCE on a same cell.

In one embodiment, the first MAC CE indicates beam failure informationassociated with the first cell and the second cell

In one embodiment, the second MAC CE indicates beam failure informationassociated with the second cell. The second MAC CE does not indicatebeam failure information associated with the first cell.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to beconfigured, by a base station, with a first cell and a second cell, (ii)to trigger a first BFR associated with the first cell, (iii) to triggera second BFR associated with the second cell, (iv) to generate a firstMAC CE in response to the first (triggered) BFR and/or the (triggered)second BFR, (v) to perform a cell deactivation deactivating the firstcell, (vi) to generate a second MAC CE in response to the celldeactivation, and (vii) to transmit the second MAC CE to the basestation. Furthermore, the CPU 308 can execute the program code 312 toperform one, some and/or all of the above-described actions and stepsand/or others described herein.

FIG. 10 is a flow chart 1000 according to one exemplary embodiment fromthe perspective of a UE. In step 1005, the UE is configured, by a basestation, with a first cell and a second cell. In step 1010, the UEtriggers a first BFR associated with the first cell. In step 1015, theUE triggers a second BFR associated with the second cell. In step 1020,the UE generates a first MAC CE in response to the first (triggered) BFRand/or the (triggered) second BFR. In step 1025, the UE performs a celldeactivation deactivating the first cell and the second cell. In step1030, the UE does not transmit (and/or does not retransmit) the firstMAC CE in response to the cell deactivation.

In one embodiment, the UE cancels the first (triggered) BFR in responseto the cell deactivation.

In one embodiment, the UE cancels the second BFR in response to the celldeactivation.

In one embodiment, the UE stops a BFR procedure associated with thefirst (triggered) BFR and the second BFR in response to the celldeactivation (e.g., the UE may stop the BFR procedure based upon adetermination that cells, such as the first cell and/or the second cell,associated with the BFR procedure are deactivated and/or a determinationthat no cell of the cells is activated).

In one embodiment, the UE performs the cell deactivation in response toa MAC CE transmitted by the base station.

In one embodiment, the UE deactivates the first cell and the second cellin response to one or more MAC CEs transmitted by the base station,wherein the one or more MAC CEs indicate deactivation of the first celland the second cell.

In one embodiment, the UE deactivates the first cell and the second cellin response to a third MAC CE transmitted by the base station, whereinthe third MAC CE indicates deactivation of the first cell and the secondcell.

In one embodiment, the UE deactivates the first cell in response toexpiration of a timer associated with the first cell.

In one embodiment, the UE deactivates the second cell in response toexpiration of a timer associated with the second cell.

In one embodiment, the first MAC CE indicates beam failure informationassociated with the first cell and the second cell.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to beconfigured, by a base station, with a first cell and a second cell, (ii)to trigger a first BFR associated with the first cell, (iii) to triggera second BFR associated with the second cell, (iv) to generate a firstMAC CE in response to the first (triggered) BFR and/or the (triggered)second BFR, (v) to perform a cell deactivation deactivating the firstcell and the second cell, and (vi) to not transmit (and/or to notretransmit) the first MAC CE in response to the cell deactivation.Furthermore, the CPU 308 can execute the program code 312 to performone, some and/or all of the above-described actions and steps and/orothers described herein.

With respect to FIGS. 9-10, in one embodiment, the first cell is a SCelland/or the second cell is a SCell.

In one embodiment, the first cell is a PCell and/or the second cell is aPCell.

In one embodiment, the UE is configured with one or more cells inaddition to the first cell and the second cell.

In one embodiment, beam failure information indicates one or more cellidentities of one or more associated cells. In an example where the beamfailure information is associated with the first cell and the secondcell, the beam failure information may indicate a first cell identityassociated with the first cell and a second cell identity associatedwith the second cell.

In one embodiment, beam failure information indicates one or morecandidate beams (e.g., one or more candidate beam indexes) for BFR ofone or more associated cells. In an example where the beam failureinformation is associated with the first cell and the second cell, thebeam failure information may indicate one or more first candidate beams(e.g., one or more first candidate beam indexes) for BFR of the firstcell and one or more second candidate beams (e.g., one or more secondcandidate beam indexes) for BFR of the second cell.

In one embodiment, the BFR procedure associated with one or more BFRs(such as the first (triggered) BFR and/or the second (triggered) BFR)comprises transmitting a SR to the base station.

In one embodiment, the BFR procedure associated with one or more BFRs(such as the first (triggered) BFR and/or the (triggered) second BFR)comprises transmitting (and/or retransmitting) a MAC CE, associated withthe one or more BFRs, to the base station.

In one embodiment, a BFR associated with a cell (e.g., the first(triggered) BFR associated with the first cell and/or the second(triggered) BFR associated with the second cell) is triggered inresponse to one or more beam failure indications (e.g., one or more beamfailure indications associated with the cell) received from a lowerlayer of the UE.

FIG. 11 is a flow chart 1100 according to one exemplary embodiment fromthe perspective of a UE. In step 1105, the UE triggers a first BFRassociated with a cell. In step 1110, the UE performs a BFR procedure inresponse to the first triggered BFR. In step 1115, the UE cancels thefirst triggered BFR in response to deactivation of the cell. In step1120, the UE stops the BFR procedure, if the UE does not have othercells associated with a second triggered BFR, in response to thedeactivation of the cell (e.g., in response to the deactivation of thecell, the UE may stop the BFR procedure if the UE does not have anyactivated cell associated with the second triggered BFR).

In one embodiment, the BFR procedure comprises transmitting a SRassociated with the first triggered BFR and/or the second triggered BFR.

In one embodiment, the BFR procedure comprises transmitting a BFR MAC CEassociated with the first triggered BFR and/or the second triggered BFR.

In one embodiment, the UE does not stop the BFR procedure (such as inresponse to the deactivation of the cell) if there is an activated cell(e.g., an activated cell that the UE is configured with) associated withthe second triggered BFR.

In one embodiment, the UE generates a BFR MAC CE if the first triggeredBFR is not canceled and if one or more UL-SCH resources are availablefor accommodating the BFR MAC CE and a subheader of the BFR MAC CE(e.g., the UE may generate the BFR MAC CE if the first triggered BFR isnot canceled and if one or more UL-SCH resources, that can accommodatethe BFR MAC CE and the subheader of the BFR MAC CE, are available).

In one embodiment, the UE triggers a SR for SCell beam failure recoveryif the first triggered BFR is not canceled and if UL-SCH resources arenot available for accommodating a BFR MAC CE and a subheader of the BFRMAC CE (e.g., the UE may trigger the SR for SCell beam failure recoveryif the first triggered BFR is not canceled and if UL-SCH resources thatcan accommodate the BFR MAC CE and the subheader of the BFR MAC CE areunavailable).

In one embodiment, the UE cancels a (triggered) SR (associated with thecell), that is triggered for the first triggered BFR, in response to thedeactivation of the cell.

In one embodiment, the cell is a SCell associated with a Master CellGroup (MCG) or a Secondary Cell Group (SCG).

In one embodiment, the UE stops a random access procedure, that isinitiated in response to the first triggered BFR, in response to thedeactivation of the cell.

In one embodiment, the deactivation of the cell is in response to the UEreceiving a SCell Activation/Deactivation MAC CE from a base station(e.g., a SCell Deactivation MAC CE that indicates (and/or is for)deactivation of the cell).

In one embodiment, the deactivation of the cell is in response toexpiration of a timer.

In one embodiment, the BFR procedure is used and/or performed forindicating information to a serving gNB in response to detecting beamfailure on one or more serving SSBs and/or one or more serving CSI-RSs(and/or the BFR procedure may be used and/or performed for indicatingthe information to the serving gNB when beam failure on the one or moreserving SSBs and/or the one or more serving CSI-RSs is detected). Theinformation may comprise a new SSB (e.g., a SSB different from the oneor more serving SSBs) and/or a new CSI-RS (e.g., a CSI-RS different fromthe one or more serving CSI-RSs).

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to trigger afirst BFR associated with a cell, (ii) to perform a BFR procedure inresponse to the first triggered BFR, (iii) to cancel the first triggeredBFR in response to deactivation of the cell, and (iv) to stop the BFRprocedure, if the UE does not have other cells associated with a secondtriggered BFR, in response to the deactivation of the cell. Furthermore,the CPU 308 can execute the program code 312 to perform one, some and/orall of the above-described actions and steps and/or others describedherein.

FIG. 12 is a flow chart 1200 according to one exemplary embodiment fromthe perspective of a UE. In step 1205, the UE triggers a first BFRassociated with a first cell. In step 1210, the UE triggers a SR forSCell beam failure recovery in response to the first triggered BFR. Forexample, the UE may trigger the SR for SCell beam failure recovery inresponse to the first triggered BFR being triggered by the UE. In step1215, the UE cancels the first triggered BFR and the triggered SR forSCell beam failure recovery associated with the first cell in responseto deactivation of the first cell.

In one embodiment, in response to the deactivation of the first cell,the UE stops transmission of SR or SR transmission for SCell beamfailure recovery if the UE does not have a cell (e.g., an activatedcell), other than the first cell, associated with a second triggeredBFR. In an example, in response to the deactivation of the first cell,the UE may not transmit the SR for SCell beam failure recovery if the UEdoes not have a cell (e.g., an activated cell), other than the firstcell, associated with a second triggered BFR.

In one embodiment, in response to the deactivation of the first cell,the UE may not stop transmission of SR or SR transmission for SCell beamfailure recovery if the UE has a cell (e.g., an activated cell), otherthan the first cell, associated with a second triggered BFR. In anexample, in response to the deactivation of the first cell, the UE maytransmit SR for SCell beam failure recovery if the UE has a cell (e.g.,an activated cell), other than the first cell, associated with a secondtriggered BFR.

In one embodiment, in response to the deactivation of the first cell,the UE stops transmission of the SR or the SR transmission for SCellbeam failure recovery if there are not any cells (with which the UE isconfigured) that are activated and are associated with a triggered BFR.In an example, in response to the deactivation of the first cell, the UEmay not transmit the SR for SCell beam failure recovery if there are notany cells (with which the UE is configured) that are activated and areassociated with a triggered BFR.

In one embodiment, prior to the canceling the first triggered BFR, theUE generates a BFR MAC CE if one or more UL-SCH resources, foraccommodating the BFR MAC CE and a subheader of the BFR MAC CE, areavailable. In an example, the UE may generate the BFR MAC CE if thefirst triggered BFR is not canceled and the one or more UL-SCHresources, for accommodating the BFR MAC CE and the subheader of the BFRMAC CE, are available. In an example, the UE may generate the BFR MAC CEif the first triggered BFR is not canceled and one or more UL-SCHresources, that can accommodate transmission of the BFR MAC CE and thesubheader of the BFR MAC CE, are available.

In one embodiment, the UE triggers the SR for SCell beam failurerecovery based upon the first triggered BFR not being canceled and basedupon an unavailability of UL-SCH resources for accommodating a BFR MACCE and a subheader of the BFR MAC CE. For example, in response to thefirst triggered BFR, the UE may trigger the SR for SCell beam failurerecovery if the first triggered BFR is not canceled and one or moreUL-SCH resources that can accommodate transmission of a BFR MAC CE and asubheader of the BFR MAC CE are unavailable.

In one embodiment, the first cell is a SCell associated with a MCG or aSCG. For example, the MCG or the SCG may comprise the first cell.

In one embodiment, the UE initiates a random access procedure inresponse to the first triggered BFR. For example, the UE may trigger therandom access procedure in response to the first triggered BFR beingtriggered by the UE. In response to the deactivation of the first cell,the UE stops the random access procedure.

In one embodiment, the deactivation of the first cell is performed inresponse to the UE receiving a MAC CE (e.g., a SCellActivation/Deactivation MAC CE), associated with SCell Deactivation,from a base station, or in response to expiration of a SCelldeactivation timer.

In one embodiment, the UE determines whether or not to trigger the firstBFR based upon whether or not the first cell is a SCell. For example,the UE may determine to trigger the first BFR based upon the first cellbeing a SCell.

In one embodiment, the UE transmits the SR for SCell beam failurerecovery on a second cell different from the first cell. In other words,the UE performs the SR transmission for SCell beam failure recovery on asecond cell different from the first cell.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to trigger afirst BFR associated with a first cell, (ii) to trigger a SR for SCellbeam failure recovery in response to the first triggered BFR, and (iii)to cancel the first triggered BFR and the triggered SR for SCell beamfailure recovery associated with the first cell in response todeactivation of the first cell. Furthermore, the CPU 308 can execute theprogram code 312 to perform one, some and/or all of the above-describedactions and steps and/or others described herein.

FIG. 13 is a flow chart 1300 according to one exemplary embodiment fromthe perspective of a UE. In step 1305, the UE triggers a first BFRassociated with a first cell. In step 1310, the UE triggers a SR forSCell beam failure recovery in response to the first triggered BFR. Forexample, the UE may trigger the SR for SCell beam failure recovery inresponse to the first triggered BFR being triggered by the UE. In step1315, in response to deactivation of the first cell, the UE cancels thefirst triggered BFR and one of stops transmission of SR or SRtransmission for SCell beam failure recovery if the UE does not have anactivated cell associated with a triggered BFR, or does not stoptransmission of the SR or the SR transmission for SCell beam failurerecovery if the UE has an activated cell associated with a secondtriggered BFR.

In an example, in response to the deactivation of the first cell, the UEstops transmission of SR or SR transmission for SCell beam failurerecovery (and/or the UE may not transmit the SR for SCell beam failurerecovery) if there are not any cells (with which the UE is configured)that are activated and are associated with a triggered (and/or pending)BFR.

In an example, in response to the deactivation of the first cell, the UEdoes not stop transmission of SR or SR transmission for SCell beamfailure recovery (and/or the UE may transmit the SR for SCell beamfailure recovery) if one or more cells (with which the UE is configured)are activated and are associated with a triggered (and/or pending) BFR.

In one embodiment, the deactivation of the first cell is performed inresponse to the UE receiving a MAC CE (e.g., a SCellActivation/Deactivation MAC CE), associated with SCell deactivation,from a base station, or in response to expiration of a SCelldeactivation timer.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to trigger afirst BFR associated with a first cell, (ii) to trigger a SR for SCellbeam failure recovery in response to the first triggered BFR, and (iii)in response to deactivation of the first cell, to cancel the firsttriggered BFR and one of: stop transmission of SR or SR transmission forSCell beam failure recovery if the UE does not have an activated cellassociated with a triggered BFR; or not stop transmission of the SR orthe SR transmission for SCell beam failure recovery if the UE has anactivated cell associated with a second triggered BFR. Furthermore, theCPU 308 can execute the program code 312 to perform one, some and/or allof the above-described actions and steps and/or others described herein.

To enhance 3GPP specification for wireless communication in accordancewith some embodiments herein, Enhancement 1, Enhancement 2 andEnhancement 3 are provided herein. Each of Enhancements 1-3 isreflective of implementation in accordance with some embodiments herein,and comprises an addition to a list of acts in Section 5.9 of 3GPP TS38.321, V15.7.0. The list of acts corresponds to acts that may beperformed by a device if a SCell Activation/Deactivation MAC CE thatdeactivates a SCell is received, or if a timer (e.g.,sCellDeactivationTimer) associated with the SCell expires. A portion ofSection 5.9 of 3GPP TS 38.321, V15.7.0, which contains the list of acts,is quoted below, where conditions upon which a device may perform one ormore acts of the list of acts are preceded by “1>” and list items of thelist of acts are preceded by “2>”:

-   -   1> else if an SCell Activation/Deactivation MAC CE is received        deactivating the SCell; or    -   1> if the sCellDeactivationTimer associated with the activated        SCell expires:        -   2> deactivate the SCell according to the timing defined in            TS 38.213 [6];        -   2> stop the sCellDeactivationTimer associated with the            SCell;        -   2> stop the bwp-InactivityTimer associated with the SCell;        -   2> deactivate any active BWP associated with the SCell;        -   2> clear any configured downlink assignment and any            configured uplink grant Type 2 associated with the SCell            respectively;        -   2> clear any PUSCH resource for semi-persistent CSI            reporting associated with the SCell;        -   2> suspend any configured uplink grant Type 1 associated            with the SCell;        -   2> flush all HARQ buffers associated with the SCell.

In Enhancement 1, an additional list item is added to the list of actsin accordance with some embodiments of the present disclosure. Theadditional list item of Enhancement 1 corresponds to an act of stoppingtransmission of SRs or SR transmissions associated with BFR associatedwith a SCell (e.g., the SCell is deactivated). A modified version of theportion of Section 5.9 of 3GPP TS 38.321, V15.7.0, containing theadditional list item of Enhancement 1, is provided below. The additionallist item of Enhancement 1 is preceded by the term “ADDITIONAL LISTITEM:” to distinguish the additional list item from other list itemsoriginally included in Section 5.9 of 3GPP TS 38.321, V15.7.0.

Enhancement 1:

-   -   1> else if an SCell Activation/Deactivation MAC CE is received        deactivating the SCell; or    -   1> if the sCellDeactivationTimer associated with the activated        SCell expires:        -   2> deactivate the SCell according to the timing defined in            TS 38.213 [6];        -   2> stop the sCellDeactivationTimer associated with the            SCell;        -   2> stop the bwp-InactivityTimer associated with the SCell;        -   2> deactivate any active BWP associated with the SCell;        -   2> clear any configured downlink assignment and any            configured uplink grant Type 2 associated with the SCell            respectively;        -   2> clear any PUSCH resource for semi-persistent CSI            reporting associated with the SCell;        -   2> suspend any configured uplink grant Type 1 associated            with the SCell;        -   2> flush all HARQ buffers associated with the SCell;        -   ADDITIONAL LIST ITEM:        -   2> stop transmitting Scheduling requests associated with            beam failure recovery associated with the SCell.

In Enhancement 2, an additional list item is added to the list of actsin accordance with some embodiments of the present disclosure. Theadditional list item of Enhancement 2 corresponds to an act of stoppingtransmission of a BFR MAC CE if the BFR MAC CE reports beam failure ofonly a SCell, such as a deactivated SCell (e.g., the transmission of theBFR MAC CE may be stopped if the BFR MAC CE does not report beam failureof one or more cells other than the SCell). A modified version of theportion of Section 5.9 of 3GPP TS 38.321, V15.7.0, containing theadditional list item of Enhancement 2, is provided below. The additionallist item of Enhancement 2 is preceded by the term “ADDITIONAL LISTITEM:” to distinguish the additional list item from other list itemsoriginally included in Section 5.9 of 3GPP TS 38.321, V15.7.0.

Enhancement 2:

-   -   1> else if an SCell Activation/Deactivation MAC CE is received        deactivating the SCell; or    -   1> if the sCellDeactivationTimer associated with the activated        SCell expires:        -   2> deactivate the SCell according to the timing defined in            TS 38.213 [6];        -   2> stop the sCellDeactivationTimer associated with the            SCell;        -   2> stop the bwp-InactivityTimer associated with the SCell;        -   2> deactivate any active BWP associated with the SCell;        -   2> clear any configured downlink assignment and any            configured uplink grant Type 2 associated with the SCell            respectively;        -   2> clear any PUSCH resource for semi-persistent CSI            reporting associated with the SCell;        -   2> suspend any configured uplink grant Type 1 associated            with the SCell;        -   2> flush all HARQ buffers associated with the SCell;        -   ADDITIONAL LIST ITEM:        -   2> stop transmitting BFR MAC CE if the BFR MAC CE reports            beam failure of only the SCell.

In Enhancement 3, an additional list item is added to the list of actsin accordance with some embodiments of the present disclosure. Theadditional list item of Enhancement 3 corresponds to an act of stoppingtransmission of a BFR MAC CE if SCells reported by the BFR MAC CE (e.g.,one or more SCells for which beam failure is indicated by the BFR MACCE) are all deactivated (e.g., the additional list item may correspondto an act of stopping transmission of a BFR MAC CE if all SCellsreported by the BFR MAC CE are deactivated). A modified version of theportion of Section 5.9 of 3GPP TS 38.321, V15.7.0, containing theadditional list item of Enhancement 3, is provided below. The additionallist item of Enhancement 3 is preceded by the term “ADDITIONAL LISTITEM:” to distinguish the additional list item from other list itemsoriginally included in Section 5.9 of 3GPP TS 38.321, V15.7.0.

Enhancement 3:

-   -   1> else if an SCell Activation/Deactivation MAC CE is received        deactivating the SCell; or    -   1> if the sCellDeactivationTimer associated with the activated        SCell expires:        -   2> deactivate the SCell according to the timing defined in            TS 38.213 [6];        -   2> stop the sCellDeactivationTimer associated with the            SCell;        -   2> stop the bwp-InactivityTimer associated with the SCell;        -   2> deactivate any active BWP associated with the SCell;        -   2> clear any configured downlink assignment and any            configured uplink grant Type 2 associated with the SCell            respectively;        -   2> clear any PUSCH resource for semi-persistent CSI            reporting associated with the SCell;        -   2> suspend any configured uplink grant Type 1 associated            with the SCell;        -   2> flush all HARQ buffers associated with the SCell;        -   ADDITIONAL LIST ITEM:        -   2> stop transmitting BFR MAC CE if SCells reported by the            BFR MAC CE are all deactivated.

A communication device (e.g., a UE, a base station, a network node,etc.) may be provided, wherein the communication device may comprise acontrol circuit, a processor installed in the control circuit and/or amemory installed in the control circuit and coupled to the processor.The processor may be configured to execute a program code stored in thememory to perform method steps illustrated in FIGS. 9-13. Furthermore,the processor may execute the program code to perform one, some and/orall of the above-described actions and steps and/or others describedherein.

A computer-readable medium may be provided. The computer-readable mediummay be a non-transitory computer-readable medium. The computer-readablemedium may comprise a flash memory device, a hard disk drive, a disc(e.g., a magnetic disc and/or an optical disc, such as at least one of adigital versatile disc (DVD), a compact disc (CD), etc.), and/or amemory semiconductor, such as at least one of static random accessmemory (SRAM), dynamic random access memory (DRAM), synchronous dynamicrandom access memory (SDRAM), etc. The computer-readable medium maycomprise processor-executable instructions, that when executed causeperformance of one, some and/or all method steps illustrated in FIGS.9-13, and/or one, some and/or all of the above-described actions andsteps and/or others described herein.

It may be appreciated that applying one or more of the techniquespresented herein may result in one or more benefits including, but notlimited to, increased efficiency of communication between devices (e.g.,a UE and/or a network node). The increased efficiency may be a result ofenabling a UE to avoid unnecessarily performing operations of a BFRprocedure when a cell (e.g., a SCell) associated with the BFR procedureis deactivated.

Various aspects of the disclosure have been described above. It shouldbe apparent that the teachings herein may be embodied in a wide varietyof forms and that any specific structure, function, or both beingdisclosed herein is merely representative. Based on the teachings hereinone skilled in the art should appreciate that an aspect disclosed hereinmay be implemented independently of any other aspects and that two ormore of these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. As an exampleof some of the above concepts, in some aspects concurrent channels maybe established based on pulse repetition frequencies. In some aspectsconcurrent channels may be established based on pulse position oroffsets. In some aspects concurrent channels may be established based ontime hopping sequences. In some aspects concurrent channels may beestablished based on pulse repetition frequencies, pulse positions oroffsets, and time hopping sequences.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, processors, means, circuits, and algorithmsteps described in connection with the aspects disclosed herein may beimplemented as electronic hardware (e.g., a digital implementation, ananalog implementation, or a combination of the two, which may bedesigned using source coding or some other technique), various forms ofprogram or design code incorporating instructions (which may be referredto herein, for convenience, as “software” or a “software module”), orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentdisclosure.

In addition, the various illustrative logical blocks, modules, andcircuits described in connection with the aspects disclosed herein maybe implemented within or performed by an integrated circuit (“IC”), anaccess terminal, or an access point. The IC may comprise a generalpurpose processor, a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, electrical components, opticalcomponents, mechanical components, or any combination thereof designedto perform the functions described herein, and may execute codes orinstructions that reside within the IC, outside of the IC, or both. Ageneral purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

It is understood that any specific order or hierarchy of steps in anydisclosed process is an example of a sample approach. Based upon designpreferences, it is understood that the specific order or hierarchy ofsteps in the processes may be rearranged while remaining within thescope of the present disclosure. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with theaspects disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module (e.g., including executable instructions and relateddata) and other data may reside in a data memory such as RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a harddisk, a removable disk, a CD-ROM, or any other form of computer-readablestorage medium known in the art. A sample storage medium may be coupledto a machine such as, for example, a computer/processor (which may bereferred to herein, for convenience, as a “processor”) such theprocessor can read information (e.g., code) from and write informationto the storage medium. A sample storage medium may be integral to theprocessor. The processor and the storage medium may reside in an ASIC.The ASIC may reside in user equipment. In the alternative, the processorand the storage medium may reside as discrete components in userequipment. Alternatively and/or additionally, in some aspects anysuitable computer-program product may comprise a computer-readablemedium comprising codes relating to one or more of the aspects of thedisclosure. In some aspects a computer program product may comprisepackaging materials.

While the disclosed subject matter has been described in connection withvarious aspects, it will be understood that the disclosed subject matteris capable of further modifications. This application is intended tocover any variations, uses or adaptation of the disclosed subject matterfollowing, in general, the principles of the disclosed subject matter,and including such departures from the present disclosure as come withinthe known and customary practice within the art to which the disclosedsubject matter pertains.

1. A method of a User Equipment (UE) configured with multiple cellscomprising a first cell and a second cell, the method comprising:triggering a first beam failure recovery (BFR) in response to a beamfailure indication for the first cell; and responsive to deactivation ofthe first cell associated with the beam failure indication thattriggered the first triggered BFR, canceling the first triggered BFRassociated with the first cell, wherein the first cell is a SecondaryCell (SCell) of the UE and the second cell is a Primary Cell (PCell) ofthe UE.
 2. The method of claim 1, comprising: responsive to thedeactivation of the first cell, stopping Scheduling Request (SR)transmission for SCell beam failure recovery if the UE does not have acell, other than the first cell, associated with a second triggered BFR.3. The method of claim 1, comprising: responsive to the deactivation ofthe first cell, not stopping Scheduling Request (SR) transmission forSCell beam failure recovery if the UE has an activated cell, other thanthe first cell, associated with a second triggered BFR.
 4. The method ofclaim 1, comprising: prior to the canceling the first triggered BFR,generating a BFR Medium Access Control (MAC) Control Element (CE) if oneor more Uplink Shared Channel (UL-SCH) resources, for accommodating theBFR MAC CE and a subheader of the BFR MAC CE, are available.
 5. Themethod of claim 1, comprising: triggering a Scheduling Request (SR) forSCell beam failure recovery based upon the first triggered BFR not beingcanceled and based upon an unavailability of Uplink Shared Channel(UL-SCH) resources for accommodating a BFR Medium Access Control (MAC)Control Element (CE) and a subheader of the BFR MAC CE.
 6. The method ofclaim 1, comprising: responsive to the first triggered BFR, initiating arandom access procedure on a Special Cell (SpCell); and responsive tothe deactivation of the first cell, stopping the random accessprocedure.
 7. The method of claim 1, wherein: the deactivation of thefirst cell is performed responsive to: receiving a Medium Access Control(MAC) Control Element (CE), associated with SCell deactivation, from abase station; or expiration of a SCell deactivation timer.
 8. The methodof claim 1, comprising: determining to not trigger a second BFRassociated with the second cell based upon the second cell being thePCell of the UE.
 9. The method of claim 1, comprising: performingScheduling Request (SR) transmission for SCell beam failure recovery onthe second cell is performed responsive to: the triggered SR for SCellbeam failure recovery triggered responsive to the first triggered BFRassociated with the first cell.
 10. A User Equipment (UE) configuredwith multiple cells comprising a first cell and a second cell, the UEcomprising: a control circuit; a processor installed in the controlcircuit; and a memory installed in the control circuit and operativelycoupled to the processor, wherein the processor is configured to executea program code stored in the memory to perform operations, theoperations comprising: triggering a first beam failure recovery (BFR) inresponse to a beam failure indication for the first cell; and responsiveto deactivation of the first cell associated with the beam failureindication that triggered the first triggered BFR, canceling the firsttriggered BFR associated with the first cell, wherein the first cell isa Secondary Cell (SCell) of the UE and the second cell is a Primary Cell(PCell) of the UE.
 11. The UE of claim 10, the operations comprising:responsive to the deactivation of the first cell, stopping SchedulingRequest (SR) transmission for SCell beam failure recovery if the UE doesnot have a cell, other than the first cell, associated with a secondtriggered BFR.
 12. The UE of claim 10, the operations comprising:responsive to the deactivation of the first cell, not stoppingScheduling Request (SR) transmission for SCell beam failure recovery ifthe UE has an activated cell, other than the first cell, associated witha second triggered BFR.
 13. The UE of claim 10, the operationscomprising: prior to the canceling the first triggered BFR, generating aBFR Medium Access Control (MAC) Control Element (CE) if one or moreUplink Shared Channel (UL-SCH) resources, for accommodating the BFR MACCE and a subheader of the BFR MAC CE, are available.
 14. The UE of claim10, the operations comprising: triggering a Scheduling Request (SR) forSCell beam failure recovery based upon the first triggered BFR not beingcanceled and based upon an unavailability of Uplink Shared Channel(UL-SCH) resources for accommodating a BFR Medium Access Control (MAC)Control Element (CE) and a subheader of the BFR MAC CE.
 15. The UE ofclaim 10, the operations comprising: responsive to the first triggeredBFR, initiating a random access procedure on a Special Cell (SpCell);and responsive to the deactivation of the first cell, stopping therandom access procedure.
 16. The UE of claim 10, wherein: thedeactivation of the first cell is performed responsive to: receiving aMedium Access Control (MAC) Control Element (CE), associated with SCelldeactivation, from a base station; or expiration of a SCell deactivationtimer.
 17. The UE of claim 10, the operations comprising: determining tonot trigger a second BFR associated with the second cell based upon thesecond cell being the PCell of the UE.
 18. The UE of claim 10, theoperations comprising: performing Scheduling Request (SR) transmissionfor SCell beam failure recovery on the second cell is performedresponsive to: the triggered SR for SCell beam failure recoverytriggered responsive to the first triggered BFR associated with thefirst cell.
 19. A non-transitory computer-readable medium comprisingprocessor-executable instructions that, when executed by a UserEquipment (UE) configured with multiple cells comprising a first celland a second cell, cause performance of operations, the operationscomprising: triggering a first beam failure recovery (BFR) in responseto a beam failure indication for the first cell; and responsive todeactivation of the first cell associated with the beam failureindication that triggered the first triggered BFR, canceling the firsttriggered BFR associated with the first cell, wherein one of the firstcell or the second cell is a Secondary Cell (SCell) of the UE andanother of the first cell or the second cell is a Primary Cell (PCell)of the UE.
 20. The non-transitory computer-readable medium of claim 19,wherein: the deactivation of the first cell is performed responsive to:receiving a Medium Access Control (MAC) Control Element (CE), associatedwith SCell deactivation, from a base station; or expiration of a SCelldeactivation timer.